home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
comm
/
cs_mac06.zip
/
WHY
< prev
Wrap
Text File
|
1992-08-23
|
2KB
|
37 lines
┌────────────────────────────────┐
│ Chuck Seyboldt's COMMO Macro │ CS-MAC06:WHY
└────────────────────────────────┘
Why?
Why take a simple one-file macro and turn it into a
convoluted four-file linked macro mess? Very good question!
There were two driving forces that I can name. One is RAM
and the other is expandability. By dividing the macro into smaller
pieces, less RAM is required at any given time. CS-MAC05 with
comments was too large to fit into memory! With four smaller
macros, I can continue to develop my own {Commo} macro environment
(with comments) and have it easily shared with others.
CS-MAC05 was also close to the limit of expandability for
new BBSware and MAILware. In several places the macro was at the
limit of 16 simultaneous {golo } and {look } strings. In CS-MAC06,
I have chosen to define particulars for each BBSware and MAILware in
a TABLE. These particulars are passed to a generic LOGON.
Of course, I have a disclaimer. What you have in your hands
is my evolving {Commo} environment. It has mistakes that I haven't
seen to repair. It is *NOT* fully developed ... I continue to
add and change in the hopes to make this environment more user
friendly.
It is my hope that some energetic {Commo} users out there
will benefit from the concepts in these macros. In the same sense
that Jeff Oberlee grew "MACROBBS" from Shad Muegge's "MOSTHOST"
maybe someone will grow "CS-MAC" into a much more feature filled
automated MAIL/FILE macro.
Chuck∙S